Systems, methods and devices for traffic offloading

ABSTRACT

Wireless communication traffic can be offloaded from a user equipment (UE) to two wireless points of access. For example, user equipment (UE) is connected to a radio access network (RAN) using a radio access technology (RAT) such as a long term evolution (LTE) network. The UE can determine which network capabilities are available for traffic offloading and adapt to the capabilities presented. In one embodiment, the UE can determine whether the network supports three different configurations and configure traffic offloading to operate within the network conditions: (1) RAN rules without access network detection and selection function (ANDSF), (2) ANDSF in conjunction with RAN rules or (3) enhanced ANDSF with RAN assistance.

RELATED APPLICATION

This application claims the benefit under 35 U.S.C. § 119(e) of U.S.Non-Provisional patent application Ser. No. 15/137,974, filed Apr. 25,2016, which is a continuation of U.S. Non-Provisional patent applicationSer. No. 14/318,098, filed Jun. 27, 2014, which claims the benefit ofU.S. Provisional Application No. 61/883,731, filed Sep. 27, 2013, bothof which are hereby incorporated by reference herein in their entirety.

TECHNICAL FIELD

The present disclosure relates to traffic offloading and moreparticularly relates to wireless traffic offload based at least in parton network information.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating a communication systemconsistent with embodiments disclosed herein.

FIG. 2 is a schematic diagram illustrating an example of user equipment(UE) and wireless local area network (WLAN) access points (APs)consistent with embodiments disclosed herein.

FIG. 3 is a schematic diagram of a method for offloading trafficconsistent with embodiments disclosed herein.

FIG. 4 is a schematic diagram of a more detailed method for offloadingtraffic consistent with embodiments disclosed herein.

FIG. 5 is a schematic diagram of an alternate method for offloadingtraffic consistent with embodiments disclosed herein.

FIG. 6 is a schematic diagram of another method for offloading trafficconsistent with embodiments disclosed herein.

FIG. 7 is a schematic block diagram of an enhanced wireless protocolstack consistent with embodiments disclosed herein.

FIG. 8 is a schematic diagram of a mobile device consistent withembodiments disclosed herein.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

A detailed description of systems and methods consistent withembodiments of the present disclosure is provided below. While severalembodiments are described, it should be understood that the disclosureis not limited to any one embodiment, but instead encompasses numerousalternatives, modifications, and equivalents. In addition, whilenumerous specific details are set forth in the following description inorder to provide a thorough understanding of the embodiments disclosedherein, some embodiments can be practiced without some or all of thesedetails. Moreover, for the purpose of clarity, certain technicalmaterial that is known in the related art has not been described indetail in order to avoid unnecessarily obscuring the disclosure.

Techniques, apparatus and methods are disclosed that enable wirelesscommunication traffic offloading between two wireless points of access.For example, a user equipment (UE) is connected to a radio accessnetwork (RAN) using a radio access technology (RAT) such as a MobileBroadband (MBB) Network (e.g., an LTE network). The UE can determinewhich network capabilities are available for traffic offloading andadapt to the capabilities presented. In one embodiment, the UE candetermine whether the network supports three different configurations:(1) RAN rules without access network detection and selection function(ANDSF), (2) ANDSF in conjunction with RAN rules or (3) enhanced ANDSFwith RAN assistance. If the UE determines that a (1) RAN rules withoutANDSF is the configuration warranted, the UE can use RAN assistanceinformation with RAN rules to determine whether to perform trafficoffloading. If the UE determines that (2) ANDSF in conjunction with RANrules configuration is warranted, RAN rules are evaluated together withANDSF, RAN assistance is used in RAN rule evaluation. If the UEdetermines that an (3) enhanced ANDSF with RAN assistance isconfiguration warranted, RAN assistance information is used to evaluateANDSF rules.

In one embodiment corresponding to the first scenario, the UE receivesoffload configuration information from RAN that describes thresholds ofnetwork quality measurements and restrictions on which packet datanetworks (PDNs) can be offloaded from LTE. The UE can obtain adescription of available networks, such as WLAN identifiers, that areavailable for traffic offloading. Using network rules based at least inpart on the thresholds, the UE can evaluate on whether to offloadtraffic to other available networks. Based on the evaluation and therestrictions, the UE can offload some of the PDNs to an availablenetwork (such as a wireless local area network (WLAN) access point(AP)).

In one embodiment corresponding to the third scenario, the UE receivesoffload configuration information from the LTE network evolved packetcore (EPC) that describes thresholds of network quality measurements andrestrictions on which packet data networks (PDNs) can be offloaded fromLTE. The UE can obtain a description of available networks, such as WLANidentifiers, that are available for traffic offloading. Using networkrules based at least in part on the thresholds, the UE can evaluate onwhether to offload traffic to other available networks. Based on theevaluation and the restrictions, the UE can offload some of the PDNs toan available network (such as a wireless local area network (WLAN)access point (AP)).

In another embodiment, traffic offloading can also occur in the oppositedirection. A user equipment (UE) is connected to a WLAN AP. The UEreceives offload configuration information from the EPC that describesthresholds of network quality measurements and restrictions on whichpacket data networks (PDNs) can be offloaded from the WLAN. The UE canobtain a description of available networks, such as evolved node B (eNBor eNodeB) identifiers, that are available for traffic offloading viaLTE. Using network rules based at least in part on the thresholds, theUE can evaluate on whether to offload traffic to other availablenetworks. Based on the evaluation and the restrictions, the UE canoffload some of the PDNs to an available network (such as an eNB).

Wireless mobile communication technology uses various standards andprotocols to transmit data between a base station and a wireless mobiledevice. Wireless communication system standards and protocols caninclude the 3rd Generation Partnership Project (3GPP) long termevolution (LTE) standard; the Institute of Electrical and ElectronicsEngineers (IEEE) 802.16 standard, which is commonly known to industrygroups as worldwide interoperability for microwave access (WiMAX); andthe IEEE 802.11 standard, which is commonly known to industry groups asWi-Fi. In 3GPP radio access networks (RANs) in LTE systems, the basestation can include Evolved Universal Terrestrial Radio Access Network(E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhancedNode Bs, eNodeBs, or eNBs) and/or Radio Network Controllers (RNCs) in anE-UTRAN, which communicate with a wireless communication device, knownas user equipment (UE).

A common goal in cellular wireless networks (such as 3GPP networks) isefficient use of licensed bandwidth. One way that a UE or other mobilewireless device, helps to reduce usage of licensed bandwidth is throughoffloading. For example, a UE is configured to connect to other types ofnetworks in addition or alternatively to a cellular wireless networkthrough which at least some data may be offloaded. In one embodiment, aUE is configured to connect to a wireless local area network (WLAN)(such as a Wi-Fi network) and route traffic flows over the WLAN toreduce the usage of bandwidth on a 3GPP or other cellular wirelessnetwork.

In the Evolved Packet System (EPS) within 3GPP, the access networkdetection and selection function (ANDSF) has defined mechanisms thatenable devices to determine which access technology is preferable forconnection and/or preferable for certain IP traffic under specificconditions, e.g., through the use of an inter-system mobility policy(ISMP) and/or inter-system routing policy (ISRP). At present, legacyANDSF policies provide limited support for parameters that are relatedto radio network conditions (however, such policies may be enhancedthrough further assistance from the radio network in some embodiments,including LTE related radio parameters). This restricts the ability ofan operator to provide policies that favor a specific 3GPP radio accesstechnology (RAT) over another one with reference to another non-3GPPspecific RAT preference.

Depending on network infrastructure, traffic offloading can be supportedusing RAN assistance, legacy ANDSF and enhanced ANDSF embodiments. In afirst embodiment (see also FIG. 4) RAN provides assistance informationsuch as offload preference indicator (OPI), WLAN thresholds (bss load,RSNI, RCPI, etc.), RAN thresholds (RSRP, etc.) and/or other information.The embodiment can be used with ANDSF, if ANDSF rules are enhanced touse such information. In a second embodiment (see also FIG. 5) RANprovides assistance information similar to solution 1. Parametersincluded in the assistance information are used by rules defined in RANspecifications such as 3GPP TS 36.304, version 12.0.0, published Mar.19, 2014 and 3GPP TS 25.304, version 12.1.0, published Mar. 19, 2014. IfANDSF is not deployed, WLAN identifiers are provided via radio resourcecontrol (RRC) signaling, open mobile alliance device management (OMA DM)or other means. If ANDSF is deployed, ANDSF rules can be evaluatedtogether with RAN rules.

Different operators can have different deployment scenarios. Whilecertain operators plan to deploy ANDSF and therefore prefer an ANDSFsolution, some other operators prefer to have a solution that does notdepend on ANDSF. A hybrid solution that works with and without ANDSF canserve the needs of many operators. Additionally, while certain operatorsmay deploy a solution based on legacy or enhanced ANDSF, roaming UEsfrom other operators may implement different solutions. Therefore, it isimportant to define how different embodiments can be implemented in thesame UE.

While many of the examples focus on a UE offloading traffic from an LTEto a WLAN, for the sake of clarity, it should be recognized thatoffloading can also occur in the opposite direction and with varyingwireless technologies (such as various radio access technologies(RATs)). For example, this functionality supportsmoving/steering/offloading traffic in both directions, i.e., fromcellular to WLAN and from WLAN to cellular. Thus, the UE and networkinfrastructure can cooperate to allow moving traffic between cellularnetworks and other wireless technologies.

FIG. 1 is a schematic diagram of a communication system 100 forproviding wireless communication services to a UE 102 or other mobilewireless device. In the embodiment shown, the system 100 includes a UEcan be in communication with a cell tower 104 and WLAN AP 106. The UE islocated in a geographic position that includes cell coverage 108 from acell tower 104 and WLAN coverage 110 from a WLAN AP 106. The cell tower104 and WLAN AP 106 include a backhaul connection to networkinfrastructure 116. The UE 102 can communicate over access link A 112with cell tower 104 and over access link B 114 with WLAN AP 106.

In one embodiment, a UE 102 is within a macro cell provided by a celltower 104. The UE 102 determines a service cannot be sufficientlyprovided by cell tower 104 over access link A 112. Using offloadconfiguration data, the UE 102 determines that at least the service canbe offloaded to another connection. The UE 102 obtains a description ofavailable networks, such as a WLAN network provided by WLAN AP 106. TheUE 102 evaluates the available networks based on a set of rules. Basedon the rules, the UE 102 determines to connect to WLAN AP 106 and steerat least some traffic over access link B 114.

For example, the UE 102 can be a cellular device communicating with aneNB as the cell tower 104 and a WLAN AP 106. The UE 102 communicateswith cell tower 104 using LTE. The UE 102 evaluates the LTE connectionover access link A 112 (such as 3GPP signal strength indicators oroffload preference indicator (OPI)) in conjunction with a rule (such asan ANDSF rule or RAN rule). The UE 102 can receive the list of availablenetworks and configuration information over ANDSF (or RAN). Using theconfiguration information, offload rules and the list of availablenetworks, the UE 102 can determine to connect to WLAN AP 106 using anIEEE 802.11 protocol. UE 102 can further evaluate which PDNs to steerover 802.11 and which protocols that remain over LTE. In someembodiments, all communications can be routed over 802.11 and UE 102 cancause the LTE hardware to go into a low power state.

The list of available networks can be received through several methods.Without ANDSF, the list of available networks can be broadcast by RAN.With ANDSF, the UE can request the list of available networks. WithANDSF the list (along with other ANDSF policies) can also be pushed tothe UE by the ANDSF server.

In another embodiment, a UE 102 is within a WLAN coverage 110 providedby WLAN AP 106. The UE 102 determines a service cannot be sufficientlyprovided by WLAN AP 106 over access link B 114. Using offloadconfiguration data, the UE 102 determines that at least the service canbe offloaded to another connection. Even if no traffic goes via LTE, theUE can remain camped on LTE (e.g., the UE does not perform 3GPP cellselection at this moment). The UE 102 evaluates the available networksbased on a set of rules. Based on the rules, the UE 102 determines tosteer at least some traffic over access link A 112.

In one embodiment, a UE 102 is within a macro cell provided by a celltower 104. The UE 102 determines a service cannot be sufficientlyprovided by cell tower 104 over access link A 112. Using offloadconfiguration data, the UE 102 determines that at least the service canbe offloaded to another connection. The UE 102 obtains a description ofavailable networks, such as a WLAN network provided by WLAN AP 106. TheUE 102 evaluates the available networks based on a set of rules. Basedon the rules, the UE 102 determines not to connect to WLAN AP 106 orother available network and does not offload traffic.

It should be recognized that a backhaul connection to networkinfrastructure is not exclusively a wired connection. Backhaul caninclude relays, point-to-point wireless, wired connections, fronthaulconnections and other connections from a receiver of an access link of aUE (such as cell tower 104 or WLAN AP 106) to network infrastructure116.

Other wireless radio access technologies (RATs) and wireless connectionscan be also be used. These RATs can include global system for mobilecommunications (GSM) networks, general packet radio services (GPRS)network, enhanced data rates for GSM Evolution (EDGE) networks, 3GPP LTEnetworks, IEEE 802.11 (Wi-Fi) and IEEE 802.16 (WorldwideInteroperability for Microwave Access (WiMAX)).

FIG. 2 is a schematic diagram illustrating an example of user equipment(UE) and wireless local area network (WLAN) access points (APs). Aplurality of UEs are connected to cell tower 104, which can include UE102. Cell tower 104 is connected to network infrastructure 116. The UE102 can also connect to available networks 204, 206 and 208. In theembodiment shown, a WiMAX base station 208 relays to WLAN AP 206 whichrelays to WLAN AP 204 which has a backhaul to network infrastructure116.

In one embodiment, UE 102 is connected to cell tower 104 and has RANrules 211 stored within. A plurality of other UEs 202 are also connectedto cell tower 104. UE 102 can receive configuration data including ANDSFrules 210 and thresholds 212 from network infrastructure and/or celltower 104. UE 102 can also perform measurements 214 a of the networkinfrastructure and/or cell tower 104. Using this configuration data, UE102 can determine that a rule or rules (210 and/or 211) for attemptingtraffic offloading is/are satisfied. The UE can measure informationabout available networks 204, 206 and 208 from network infrastructure116. The UE can receive information about available networks 204, 206and 208 as well as more rules 210 (with the aid of ANDSF), thresholds212 and measurements 214 a from network infrastructure and/or cell tower104. The UE 102 can also receive measurements 214 b, 214 c and 214 d(directly or indirectly) from available networks 204, 206 and 208. Usingrules, which can include rules 210, and measurements 214 a, 214 b, 214 cand 214 d, the UE 102 can determine one or more networks for trafficoffloading. In the embodiment shown, the UE 102 determines to connectand offload traffic with WLAN AP 204 (shown by the solid line). UE 102also retains access link A 112 with cell tower 104.

It should be recognized that when traffic moving, steering or offloadingis mentioned, it is for clarity. However, the embodiment can be modifiedto use any of the moving, steering or offloading when appropriate.

In one embodiment, a RAN (such as represented by cell tower 104 andnetwork infrastructure 116) sends assistance information (such asthresholds) via RRC. Thresholds can include LTE/UMTS (Universal MobileTelecommunications System) and WLAN thresholds. UE 102 acquires actualmeasurements for LTE/UMTS and WLAN APs (e.g., the UE 102 measurescertain values for LTE/UMTS and WLAN networks). UE 102 then comparesmeasurements acquired to the thresholds received. UE 102 can thendetermine whether to offload traffic or remain with a current RAN.

Assistance information can include thresholds coming from RAN andparameters measured by UE 102. RAN rules are defined in the following3GPP technical specifications (TS): 36.304 and 25.304

A UE can be configured to identify network capabilities and then operateusing the identified capabilities. FIGS. 3-6 show methods of trafficmoving/steering/offloading (e.g., from cellular to WLAN and from WLAN tocellular) depending on network capabilities. FIG. 3 shows a simplifiedmethod of traffic offloading. FIG. 4 shows a method of trafficoffloading using RRC. FIG. 5 shows a method of traffic offloading usinglegacy ANDSF. FIG. 6 shows a method of traffic offloading using enhancedANDSF. A UE can be configured to identify and then operate within theseidentified networks.

FIG. 3 shows a process 300 of moving/steering/offloading traffic betweena first network and a second network. The method can be accomplished bya system 100 or system 200 shown in FIGS. 1 and 2 by a UE 102, celltower 104, network infrastructure 116 and WLAN AP 106. In block 302, aUE obtains offload configuration data. In block 304, a UE obtainsdescriptions of available networks. In block 306, the UE evaluatesavailable networks based on rules. In block 308, the UE uses the ruleresults to determine which connections to route to one or more availablenetworks.

The offload configuration data can be static or dynamic. In someembodiments, the offload configuration is statically stored on the UE.In other embodiments, the offload configuration data is stored on theUE, but periodically updated by network infrastructure messages (e.g.,OMA DM). In one embodiment, the UE requests updated offloadconfiguration data from the network infrastructure on demand.

FIG. 4 shows a process 400 of moving/steering/offloading traffic betweena first network and a second network. The method can be accomplished bya system 100 or system 200 shown in FIGS. 1 and 2 by a UE 102, celltower 104, network infrastructure 116 and WLAN AP 106. In the embodimentshown, an operator does not deploy ANDSF. In one embodiment, the methoddoes not support per bearer traffic steering. In block 402, a UEreceives offload configuration data from RRC signaling information. Inblock 404, the UE determines WLAN identifiers from available networks.In block 406, the UE obtains WLAN information, such as signal, load andquality information. In block 408, the UE evaluates RAN rules in lightof the offload configuration information, WLAN information and/or RANinformation. If the result of the evaluation is to connect to WLAN inblock 410, the UE determines which PDN connections to offload in block412. In block 414, the UE can then connect to the WLAN and offload thedetermined PDN connections 414. In either case in block 416, the UE canleave remaining connections with a current network.

In one embodiment, the UE operates on APN (Access Point Name) basis.APNs which should not be offloaded to WLAN, e.g., IMS APN (IP MultimediaSystem Access Point Name), may be configured to always stay on 3GPPnetwork. The information about which APNs/PDN connections may beoffloaded to WLAN may be pre-provisioned in the UE, provided as part ofan enhanced APN configuration or via some other means. When the UEdetermines to offload to WLAN it moves all bearers from all APNconnections which have been determined to be offloaded to WLAN. Asimilar process can be implemented for PDN connections.

For example, the UE acquires via broadcast or unicast RRC signaling RANinformation related to WLAN offload (e.g. 3GPP load or other parameterreflecting the load, e.g., Offload Preference Indicator), 3GPP signalstrength thresholds (e.g., RSRP threshold) and WLAN thresholds (e.g.,RSNI, RCPI and BSS load thresholds).

The UE may then optionally evaluate RAN rules based on RAN informationonly and proceed to the next steps (in which rules based on RAN and WLANinformation are evaluated) only if the rules allow offload to WLAN.Alternatively, the UE may acquire RAN and WLAN information and evaluatethe rules only when all information is available. The UE may evaluateRAN rules (defined in RAN specs) to decide whether offload to WLAN isbeneficial. RAN rules may be, for instance, of the form:

Offload to WLAN if: (RSNI > RSNI threshold 1) && (RSRP < RSRP threshold1). Stay on 3GPP if: (RSNI <= RSNI threshold 2) || (RSRP >= RSRPthreshold 2).

If the rules tell the UE to stay on the network it currently uses itdoes so, otherwise the UE proceeds to the next operation. Differentthresholds can be used in different directions to prevent UE ping-pongbetween networks (e.g., RSRP threshold 1 and RSRP threshold 2).

The UE can obtain information about WLAN networks it can access (i.e.,the UE can acquire the list of WLAN identifiers). This list can beprovided via OMA DM as defined in “Standardized Connectivity ManagementObjects, WLAN Parameters; For use with OMA Device Management; ApprovedVersion 1.0—24 Oct. 2008; OMADDSDM_ConnMO_WLANV1_020081024A” orbroadcast or unicast RRC signaling. This list can also be provided viaANDSF. Note that the UE may acquire the list of WLAN identifiers in thisoperation or in advance (e.g., when the system uses OMA DM).

Once UE acquires the list of WLAN identifiers, it acquires the WLANinformation (e.g., RSNI, RCPI, BSS load, and/or WAN metrics as definedin HotSpot 2.0 (HS2.0) by the Wi-Fi Alliance (WFA)) from WLAN networkswhich it can use (i.e., which networks are on this list). Once UEacquires WLAN and RAN information it evaluates RAN rules (defined in RANspecs) for 3GPP network it currently uses and for all WLAN networks (outof the list acquired previously) that the UE can find. RAN rules may be,for instance, of the form:

Offload to WLAN if: (OPI > OPI threshold) && (RSRP < RSRP threshold) &&(bss load < bss load threshold) && (RSSI > RSSI threshold) Stay on 3GPPif: (OPI <= OPI threshold) || (RSRP >= RSRP threshold) || (bss load >=bss load threshold) || (RSSI <= RSSI threshold)

Based on these rules, the UE decides whether to use 3GPP or WLANnetworks and which WLAN AP to connect to (if WLAN is selected) for everyPDN connection that can use both. If the rules tell the UE to use WLAN,all bearers of all PDN connections that can use WLAN are moved to WLAN.The UE may use WLCP (WLAN Link Control Protocol), defined as part ofSaMOG2 (Release12 SaMOG) WI, to establish WLAN connections and releasethese connections from EUTRAN/UTRAN. If there are multiple WLAN networksthat satisfy the selection criteria, it is left for UE implementation todecide which network to use. For example, the UE determines to selectthe WLAN AP that provides the highest QoS (according to some criteria),from amongst the APs, which also satisfies RAN rules.

In a steady state operation, the UE continues to acquire 3GPP and WLANparameters and to reevaluate RAN rules with periodicity which is leftfor UE implementation. For example, the reevaluation of RAN rules can bebased on several considerations such as latency associated withinter-RAT mobility signaling or frequency with which assistanceinformation is updated within the network. If all bearers are moved toWLAN the UE may detach from LTE. If so, the UE is expected to camp onUTRA and may acquire WLAN assistance information from UTRAN.

FIG. 5 shows a process 500 of moving/steering/offloading traffic betweena first network and a second network. The method can be accomplished bya system 100 or system 200 shown in FIGS. 1 and 2 by a UE 102, celltower 104, network infrastructure 116 and WLAN AP 106. In someembodiments, a network infrastructure operator deploys Rel-12 (orearlier) ANDSF which is not enhanced with RAN parameters. In block 502,the UE obtains offload configuration data. In block 504, the UE obtainsANDSF rules from the network infrastructure. In block 506, the UEevaluates RAN and/or ANDSF rules to determine a set of access networks.In block 508, the UE obtains available access network identifiers fromnetworks available to the UE (e.g., in range of the UE). In block 510,the UE obtains available access network information (e.g., load,strength and quality information) about available access networkidentifiers. In block 511, the UE evaluates offload rules in view ofavailable access network information. Based on the results of theevaluation in block 511, the UE determines whether to connect to adifferent network in block 512. If so and in block 514, the UEdetermines which PDN connections (or IP flow, depending on offloadgranularity) to offload to the different network. In block 516, the UEconnects to the different network and offloads determined PDNconnections. Then in block 518, whether or not the UE connects to thedifferent network, the UE leaves remaining connections with the currentnetwork.

For example, similar to FIG. 4, the initial operations may optionally beperformed. The UE acquires via broadcast or unicast RRC signaling RANinformation related to WLAN offload (e.g., 3GPP load or other parameterreflecting the load), 3GPP signal strength thresholds (e.g., RSRPthreshold) and WLAN thresholds (e.g., RSSI and BSS load thresholds).

The UE may then optionally evaluate RAN rules based on RAN informationonly and proceed to the next steps (in which rules based on RAN and WLANinformation are evaluated) only if the rules allow offload to WLAN.Alternatively, the UE may acquire RAN and WLAN information and evaluatethe rules only when all information is available. The UE may evaluateRAN rules (defined in RAN specs) to decide whether offload to WLAN isbeneficial. If the evaluation is conclusive (e.g., the rules tell the UEnot to use WLAN such as when the UE is in good LTE coverage and LTE loadis very low) the UE process may stop further processing (to save power,etc. . . . ).

In one embodiment, ANDSF is used together with RAN rules in the same UE.The UE can acquire RAN assistance information (if such information isnot already acquired previously) and WLAN assistance information. The UEselects and evaluates ANDSF and/or RAN rules based on operatorpreferences.

In another embodiment, the UE acquires ANDSF rules (if not availablealready) and evaluates them. As an output of this evaluation the UE getsa list of access networks (3GPP and WLAN) it can use (including ISRP andISMP rules).

In an embodiment, the UE can acquire RAN assistance information (if suchinformation is not already acquired previously) and WLAN assistanceinformation. The UE then evaluates RAN rules in the same manner asdescribed in FIG. 4.

As a result of this evaluation the UE may remove certain (3GPP and WLAN)access networks from the list produced by the evaluation of ANDSF rules.After that the UE proceeds (following either ISRP or ISMP rules) to usethe networks which remain on that list as defined in corresponding SA2and CT1 specifications (see S2a, S2b and S2c interfaces). The UE may useWLCP (WLAN Link Control Protocol) defined as part of SaMOG2 (Release12SaMOG) WI to establish WLAN connections and release these connectionsfrom EUTRAN/UTRAN.

FIG. 6 shows a process 600 of moving/steering/offloading traffic betweena first network and a second network. The method can be accomplished bya system 100 or system 200 shown in FIGS. 1 and 2 by a UE 102, celltower 104, network infrastructure 116 and WLAN AP 106. In someembodiments, the operator of network infrastructure deploys ANDSF whichis enhanced with RAN parameters. In block 602, the UE obtains offloadconfiguration data. In block 604, the UE receives WLAN identifiersdescribing available WLAN APs. In block 606, the UE determines WLANinformation about WLAN APs. In block 608, the UE receives networkprovider rules (such as by enhanced ANDSF). In block 610, the UEevaluates the network provider rules in view of the obtainedinformation. In block 612, the UE determines a set of access networks(which can include WLAN APs) available for use. If the UE determines toconnect to a WLAN AP (or other RAN) in block 614, the UE can determinewhich PDN connections or IP flows to offload in block 616. In block 618,the UE can connect to the WLAN AP and offload determined PDNconnections. In either case and in block 620, the UE can leave remainingconnections with a current network.

For example, the UE can acquire RAN and WLAN assistance information asdescribed in connection with FIGS. 4 and 5. The UE then evaluates ANDSFrules that are enhanced to take RAN and WLAN assistance information. Theenhanced ANDSF rules can be defined as depending on nodes. WLAN relatedANDSF nodes may have subnodes for WLAN parameters (e.g., “maximum BSSload,” “minimum RSSI,” etc.). 3GPP related ANDSF nodes may have subnodesfor RAN parameters (e.g., “maximum load,” “minimum RSRP,” etc.).Thresholds for these rules can be initially provided via ANDSF. Signalstrength values (RSSI, RSRP, etc.) can be measured by the UE. Loadvalues (cellular load, BSS load) can be provided by the network (RAN orWLAN).

Additionally in some embodiments, RAN may override signal strength(RSRP, RSNI, etc.) thresholds via RRC signaling. If RAN provides thesethresholds the UE replaces them in all ANDSF rules.

The UE can then proceed according to ISRP or ISMP rules as defined incorresponding SA2 and CT1 specifications (see S2a, S2b and S2cinterfaces). The UE may use WLCP (WLAN Link Control Protocol) defined aspart of SaMOG2 (Release12 SaMOG) WI to establish WLAN connections andrelease these connections from EUTRAN/UTRAN.

Various embodiments described herein can also be used to expand, update,use and/or provide new functionality to existing wireless systems (e.g.,RATs, RANs, UTRAN, EUTRAN, etc.). In FIG. 7, an example of an enhancedLTE protocol stack 1000 for a UE is shown. The protocol stack 700 can beenhanced with new messages 716 and measurements 718 for use inconnecting with small cells.

The stack describes protocol layers in an enhanced LTE protocol stack700. These layers can provide abstraction from a lower layer(represented as a layer closer to the bottom of the page). A physicallayer (L1) 714 includes systems that translate physical signals intological data for use by the higher layers. L1 can also providemeasurement and configuration services to the radio resource control(RRC) layer 706. The medium access control (MAC) layer 712 includessystems that perform transport as logical mapping and/or scheduling. TheMAC layer 712 includes systems that can provide format selection andmeasurements about the network to the RRC layer 706. The radio linkcontrol (RLC) layer 710 includes systems that provide segmentation,concatenation and reassembly, and can operate in different modesdepending on a radio bearer. The packet data convergence protocol (PDCP)layer 708 includes systems that can provide services for higher levelprotocols including cryptographic functions, headercompression/decompression, sequence numbering and/or duplicate removal.User traffic can be sent through the PDCP layer 708 to the internetprotocol (IP) layer 704, which is then routed to applications andsystems of the UE for use. Control traffic can be sent to the RRC layer706. The RRC layer 706 can provide management and control functions ofthe UE. RRC layer 706 functionality can include processing of broadcastinformation, paging, connection management with an eNB, integrityprotection of RRC messages, radio bearer control, mobility functions, UEmeasurement and reporting, Quality of Service management, etc. Thenon-access stratum (NAS) layer 702 includes systems that can providemobility management, call control, session management and/or identitymanagement.

The RRC layer 706 and NAS layer 702 can be further enhanced withmessages. The messages can include indicators, thresholds and rules.Indicators can include Offload Preference Indicator (OPI), ReferenceSignal Received Power (RSRP) Threshold, Reference Signal ReceivedQuality (RSRQ) Threshold, Received Channel Power Indicator (RCPI)Threshold, Received Signal Noise Indicator (RSNI) Threshold, BasicService Set (BSS) LoadThreshold and Backhaul Rate Threshold. Thresholdsand/or indicators can be static (e.g., stored statically on the UE) ordynamic (e.g., received from the network). Rules can include RadioAccess Network (RAN) Rules, Access Network Discovery & SelectionFunction (ANDSF) Rules, Inter-System Mobility Policy (ISMP),Inter-System Routing Policy (ISRP) and Inter-APN Routing Policy (IARP).

The physical layer can be enhanced with measurements to provide tolayers of the UE (e.g., an L2 layer which includes the RRC layer).Measurements can include RCPI, RSNI, RSRP, RSRQ, RSSI (Received SignalStrength Indicator), SINR (Signal to Interference plus Noise Ratio), CQI(Channel Quality Information), RSCP, CPICH RSCP (Common Pilot ChannelReceived Signal Code Power), and CPICH Ec/No (Common Pilot ChannelReceived Energy per Chip over Total Noise Power Density).

Offload configuration can include thresholds received by UE via RRC.These include: parameters (RSRP threshold for LTE), RSRQ threshold (forLTE), CPICH RSCP threshold (for UMTS), CPICH Ec/No threshold (for UMTS),OPI (for LTE or UMTS), RCPI threshold (for WLAN), RSNI threshold (forWLAN), BSS load (for WLAN) threshold and backhaul rate threshold (forWLAN). LTE/UMTS (cellular) information can include measurements made bya UE such as RSRP measurement which the UE can compare to a RSRPthreshold. WLAN information can include BSS load which a UE can compareto a BSS load threshold.

In some embodiments an Offload Preference Indicator (OPI) can be usedinstead of a load measurement.

While RRC is mentioned above, it is just one of many possibleimplementation options. Other options include other sections of thesecond protocol layer or access stratum layer (including RRC, PDCP, RLCand MAC).

Policies provided to the UE can be enhanced by having RAN assistanceinformation. For example, a policy may include multiple candidateinformation simultaneously. An example of such policy can include a 3GPPto WLAN offload environment. If RAN RSRP is less than threshold S andRAN load is greater than threshold X, and if WLAN RSSI is greater thanthreshold R and WLAN BSS load is less than threshold Y, move flow toWLAN.

An example of a WLAN to 3GPP policy includes: If RAN RSRP is greaterthan threshold S′ and RAN load is less than threshold X′, and if WLANRSSI is less than threshold R′ and WLAN BSS load is greater thanthreshold Y′, then move flow to UMTS/LTE.

In an embodiment, this policy can be realized with a new policystructure (similar to ISRP). The value of the thresholds (e.g., RANRSRP/RSCP thresholds) can be provided by RAN and used in the ANDSFpolicy. Otherwise, threshold values may also be provided by the ANDSFitself. Policies specific to the UE can be configured or pre-provisionedbased on the UE subscription. Optionally per UE control for trafficsteering can be achieved using dedicated signaling during connectedmode. For example, the RAN may send different values of the aboveparameters to different UEs in connected mode. Policies specific to atarget WLAN system (e.g., SSID or realm) can be configured orpre-provisioned. Policies and network assisted information can also beused to route some flow to WLAN and some to 3GPP.

Mechanisms can be used to avoid simultaneous massive access networkselection/traffic steering and ping-pong events (including hysteresis,randomization, different threshold values for 3GPP-to-WLAN thanWLAN-to-3GPP network selection, or thresholds on per user subscriptionlevel which may be applied to UE based decision).

FIG. 8 is an example illustration of a mobile device, such as a UE, amobile station (MS), a mobile wireless device, a mobile communicationdevice, a tablet, a handset, or another type of mobile wireless device.The mobile device can include one or more antennas configured tocommunicate with a transmission station, such as a base station (BS), aneNB, a base band unit (BBU), a remote radio head (RRH), a remote radioequipment (RRE), a relay station (RS), a radio equipment (RE), oranother type of wireless wide area network (WWAN) access point. Themobile device can be configured to communicate using at least onewireless communication standard including 3GPP LTE, WiMAX, HSPA,Bluetooth, and Wi-Fi. The mobile device can communicate using separateantennas for each wireless communication standard or shared antennas formultiple wireless communication standards. The mobile device cancommunicate in a WLAN, a wireless personal area network (WPAN), and/or aWWAN.

FIG. 8 also provides an illustration of a microphone and one or morespeakers that can be used for audio input and output from the mobiledevice. The display screen may be a liquid crystal display (LCD) screenor other type of display screen, such as an organic light emitting diode(OLED) display. The display screen can be configured as a touch screen.The touch screen may use capacitive, resistive, or another type of touchscreen technology. An application processor and a graphics processor canbe coupled to internal memory to provide processing and displaycapabilities. A non-volatile memory port can also be used to providedata input/output options to a user. The non-volatile memory port mayalso be used to expand the memory capabilities of the mobile device. Akeyboard may be integrated with the mobile device or wirelesslyconnected to the mobile device to provide additional user input. Avirtual keyboard may also be provided using the touch screen.

EXAMPLE EMBODIMENTS

Embodiments of this invention can be applied in several scenarios. Forexample, a UE is within UTRAN/E-UTRAN coverage, is using 3GPP and goesinto WLAN AP coverage. A UE is within UTRAN/E-UTRAN and WLAN coverage,is using WLAN and goes out of WLAN AP coverage. In another example, a UEis within the coverage area of both UTRAN/E-UTRAN coverage and WLANcoverage, the UE is using WLAN, and all or a subset of the UE's trafficshould be routed via UTRAN/E-UTRAN instead. In one example, a UE iswithin the coverage area of both UTRAN/E-UTRAN and WLAN, the UE is usingUTRAN/E-UTRAN, but all or a subset of the UE's traffic should be routedvia WLAN instead. In yet another example, a UE is using bothUTRAN/E-UTRAN and WLAN access and should be connected to only one (WLANor UTRAN/E-UTRAN) or some traffic should be moved to the other access.

Three embodiments are described below in WLAN-RAN based systems to aidin understanding aspects of the embodiments. It should be recognizedthat these embodiments are not exhaustive of the potential embodiments,but used to aid in understanding three possible implementations.

In a first embodiment, candidates for the WLAN-UTRAN/E-UTRAN(UTRAN/E-UTRAN are also referred to as “RAN” in the remainder of thepresent document) access network selection have been identified. RANprovides RAN assistance information to the UE through broadcastsignaling (and optionally dedicated signaling). The UE uses the RANassistance information UE thresholds and information provided by WLANand policies that are obtained via the ANDSF or via existing OMA-DMmechanisms or pre-configured at the UE to steer traffic to WLAN or toRAN.

This embodiment can be applicable to UEs in RRC IDLE and RRC CONNECTEDstates for E-UTRAN; UE IDLE mode for UTRAN; and CELL_DCH, CELL_FACH,CELL_PCH and URA_PCH states for UTRAN. Assistance parameters can includeload information (e.g., direct/indirect indication of UMTS/LTE load,e.g., in percentage, in load levels (low, medium, high) or offloadpreference indicator), resource allocation (maximum resource allocationthe UE may receive on UMTS/LTE), WLAN thresholds (WLAN RSNI threshold,WLAN RCPI, WLAN BSS load threshold and WLAN WAN metric threshold) and/orRAN thresholds (RSRP/RSCP thresholds).

In a second embodiment, the offloading rules are specified in RANspecifications. The RAN provides (through dedicated and/or broadcastsignaling) thresholds which are used in the rules. This embodiment canbe applicable to UEs in RRC IDLE and RRC CONNECTED states for E-UTRAN,UE IDLE mode for UTRAN and CELL_FACH, CELL_PCH, URA_PCH and CELL_DCHstates for UTRAN). In the embodiment, the RAN provides parametersthrough dedicated signaling and/or broadcast signaling. The UE followsRAN rules, defined in 3GPP RAN specifications, to perform bi-directionaloffloading between WLAN and 3GPP. User preference can take precedence,if so configured. Based on operator preference the UE may use ANDSFpolicies or RAN rules. An example rule is as follows:

if (measured_metricA < threshold1) && (measured_metricB > threshold2) {steerTrafficToWLAN( ); } else if (measured_metricA > threshold3) ||(measured_metricB < threshold4) { steerTrafficTo3gpp( ); }

In a third embodiment, User preference can be configured to always takesprecedence over RAN based or ANDSF based rules (e.g., when anon-operator WLAN is preferred or WLAN is off).

In an embodiment, multiple branches based on rules are possible. In afirst branch and if ANDSF is not present, the UE moves the trafficindicated in the steering command to WLAN or 3GPP as indicated. In asecond branch and when multiple Access Networks are possible accordingto the ANDSF policy, the traffic steering commands can override order ofaccess network priorities (e.g., if for certain IP flows ANDSF indicatesa prioritized order of 3GPP access and WLAN). Upon reception of acommand to steer traffic from 3GPP access to WLAN, the UE moves thecorresponding flows to WLAN. In a third branch, the dedicated trafficsteering command cannot override ANDSF in other cases (i.e., the UE willnot move traffic to an access network not indicated by ANSDF as apossibility (i.e., not indicated or indicated as forbidden)). The aboverules can apply whether the H-ANDSF or the V-ANDSF policy is active.

In one embodiment, based on operator preference/configuration, the UEselects either RAN rules or ANDSF. For example, if a roaming UE is inthe network of the operator that uses RAN rules, while a home operatordeploys ANDSF, the operator can configure the UE to ignore RAN rules andto follow ANDSF rules instead.

The above operations do not take into account user preference and/or theWLAN radio state, which can optionally affect the operations. Forexample, based on user preferences and/or WLAN radio state, a UE may notbe able to perform the configured measurement events. Additionally, theprocedures can allow a UE to be able to prioritize non-operator WLANover operator WLAN. For example, the UE may disassociate from theoperator WLAN and associate with the higher priority non-operator WLANat any time during the measurement process. In some cases, someoperations can be optional (such as measurement control and measurementreport) based on RAN/UE configuration.

The operations, and the description can apply to UMTS CELL_FACH as well.The operations can also be extended to UMTS/LTE Idle modes and UMTSCELL/URA_PCH states, e.g., UEs can be configured to report someindication (e.g., on available WLAN measurements) in a RRC UL message,e.g., RRC connection request (from Idle, in UMTS/LTE) or CELL UPDATE (inUMTS CELL/URA_PCH states).

BSSID stands for Basic Service Set Identifier: For infrastructure BSS,the BSSID is the MAC address of the wireless access point and come froma Beacon or Probe Response. SSID stands for Service Set Identifier: TheSSID can be used in multiple, possibly overlapping, BSSs and can comefrom a Beacon or Probe Response. HESSID stands for Homogeneous ExtendedService Set Identifier: A MAC address whose value shall be configured bythe Hotspot Operator with the same value as the BSSID of one of the APsin the network. All APs in the wireless network can be configured withthe same HESSID value. The HESSID can come from a Beacon or ProbeResponse or 802.11 communications. A Domain Name List element provides alist of one or more domain names of the entity operating the WLAN accessnetwork and can come from ANQP (HS 2.0). The operating class and channelnumber is an Indication of the target WLAN frequency (see Annex E of802.11 [5] for definitions of the different operating classes).

Both RCPI and RSNI can be measured by the UE. BSS Load can be obtainedby a beacon or probe response (802.11k). WAN metrics can be obtainedthrough ANQP (in HS2.0).

Examples for identifying the traffic to steer to or from WLAN caninclude DRB/RB-ID and QCI. DRB/RB-ID stands for an identity of a radiobearer. QCI stands for QoS (Quality of Service) Class Identifier.

Examples

The following examples pertain to further embodiments.

Example 1 is a mobile device comprising a mobile broadband (MBB)interface, a wireless network interface and a processor. The mobilebroadband (MBB) interface is configured for connecting to 3rd generationpartnership project (3GPP) networks. The wireless network interface isconfigured for connecting to non-MBB networks. The processor isconfigured to execute instructions that cause the mobile device toperform operations. The processor is configured to determine a MBBnetwork configuration for processing offload rules.

The processor is further configured to configure the mobile device touse offload rules compatible with the MBB network configuration. Theprocessor is also configured to determine whether to offload trafficbetween the MBB interface and the wireless network interface based onthe configured offload rules. The processor is further configured thatwhen determined to offload, the processor determines which connectionsto offload between the MBB interface and the wireless network interface.

In example 2, the processor of the mobile device of example 1 can beoptionally configured to perform more operations. The processor can beconfigured to receive offload configuration data from radio resourcecontrol (RRC) signaling. The processor can be further configured toreceive non-MBB identifiers describing available non-MBB access points(non-MBB APs) for offload of the connections. The processor can also beconfigured to obtain non-MBB information for the non-MBB identifiers.The processor can further be configured to evaluate the offload rulescomprising radio access network (RAN) rules based at least in part onthe offload configuration and the non-MBB information. The processor canalso be configured to determine to connect to a non-MBB AP. Theprocessor can be further configured to determine a set of theconnections to offload to the non-MBB AP.

In example 3, the processor of the mobile device of examples 1-2 can beoptionally configured to perform additional operations. The processorcan be further configured to obtain MBB network information comprisingoffload configuration data. The processor can also be configured toobtain offload rules comprising access network discovery and selectionfunction (ANDSF) rules. The processor can be further configured toevaluate the ANDSF rules to determine a set of access networks availablefor use, the set of access networks including a set of MBB networks anda set of non-MBB networks. The processor can also be further configuredto obtain non-MBB access network identifiers describing availablenon-MBB networks for offload of the connections. The processor can befurther configured to obtain non-MBB information for received non-MBBidentifiers. The processor can also be configured to evaluate theoffload rules based on the offload configuration, MBB networkinformation and non-MBB information. The processor can be furtherconfigured to determine a subset of the set of access networks to removefrom the set of access networks available for use. The processor canalso be configured to determine whether to connect to a non-MBB networkin the set of access networks available for use. The processor can befurther configured such that when determined to connect to the non-MBBnetwork, the processor determines which of the connections to offload tothe non-MBB network.

In example 4, the processor of the mobile device of examples 1-3 can beoptionally configured to perform additional operations. The processorcan be further configured to receive non-MBB offload configuration data.The processor can also be configured to receive non-MBB identifiersdescribing available non-MBB access points (non-MBB APs) for offload ofthe connections. The processor can be further configured to determinenon-MBB parameters for received non-MBB identifiers. The processor canalso be configured to receive offload rules comprising network providerrules that reference MBB parameters and the non-MBB parameters. Theprocessor can be further configured to evaluate the network providerrules based on the MBB parameters and non-MBB parameters. The processorcan also be configured to determine a set of access networks availablefor use. The processor can be further configured to determine whether toconnect to a non-MBB AP in the set of access networks available for use.The processor can be further configured such that when connecting to anon-MBB AP, the processor can determine which of the connections tooffload to the non-MBB AP.

Example 5 is user equipment (UE) configured to receive offloadconfiguration data from radio resource control (RRC) signaling. The UEis further configured to receive WLAN identifiers describing availablewireless local area network access points (WLAN APs) for offload ofpacket data network (PDN) connections. The UE is also configured toobtain WLAN information for the WLAN identifiers. The UE is furtherconfigured to evaluate RAN rules based at least in part on the offloadconfiguration and the WLAN information. The UE is also configured todetermine to connect to a WLAN AP. The UE is further configured todetermine a set of PDN connections to offload to the WLAN AP.

In example 6, the UE of example 5 can be optionally configured such thatthe offload configuration comprises one or more of 3rd generationpartnership project (3GPP) offload preference indicator (OPI), referencesignal received power (RSRP) threshold data, reference signal quality(RSRQ) threshold data, received signal strength indicator (RSSI)threshold data, received channel power indicator (RCPI) threshold data,received signal noise indicator (RSNI) threshold data or basic serviceset (BSS) load threshold data.

In example 7, the UE of examples 5-6 can be optionally configured suchthat receiving offload configuration further comprises evaluating theoffload configuration to determine whether the RAN rules allow offloadto WLAN and when the RAN rules do not allow offload to WLAN, stoppingfurther processing of WLAN offload evaluation.

In example 8, the UE of examples 5-7 can be optionally configured suchthat evaluating the offload configuration to determine whether the RANrules allow offload to WLAN further comprises comparing a RSRP to a RSRPthreshold or comparing RSRQ measurement to an RSRQ threshold.

In example 9, the UE of examples 5-8 can be optionally configured suchthat receiving the WLAN identifiers further comprises obtaining the WLANidentifiers by open mobile alliance device management (OMA DM) objectreceipt, radio resource control (RRC) signaling or access networkdiscovery and selection function (ANDSF).

In example 10, the UE of examples 5-9 can be optionally configured suchthat the WLAN information comprises at least one of signal strengthbasic service set (BSS) load, wide area network (WAN) metrics, receivedchannel power indicator (RCPI) or received signal noise indicator(RSNI).

In example 11, the UE of examples 5-10 can be optionally configured suchthat determining to connect to the WLAN AP further comprises selectingthe WLAN AP from a plurality of WLAN APs that satisfy the RAN rules.

Example 12 is a wireless mobile device comprising a cellular networkinterface, a wireless network interface and a processor. The cellularnetwork interface is configured for connecting to 3rd generationpartnership project (3GPP) networks. The wireless network interface isconfigured for connecting to non-3GPP networks. The processor isconfigured to execute instructions that cause the wireless mobile deviceto perform operations. The processor can be configured to obtaincellular network information comprising offload configuration data. Theprocessor can be further configured to obtain access network discoveryand selection function (ANDSF) rules. The processor can also beconfigured to evaluate the ANDSF rules to determine a set of accessnetworks available for use, the set of access networks including a setof 3GPP networks and a set of non-3GPP networks. The processor can befurther configured to obtain non-3GPP access network identifiersdescribing available non-3GPP networks for offload of packet datanetwork (PDN) connections. The processor can also be configured toobtain non-3GPP information for received non-3GPP identifiers. Theprocessor can be further configured to evaluate offload rules based onthe offload configuration, cellular network information and non-3GPPinformation to. The processor can also be configured to determine asubset of the set of access networks to remove from the set of accessnetworks available for use. The processor can be further configured todetermine whether to connect to a non-3GPP network in the set of accessnetworks available for use. The processor can also be configured suchthat when determined to connect to the non-3GPP network, the processordetermines which PDN connections to offload to the non-3GPP network.

In example 13, the UE of example 12 can be optionally configured suchthat the offload rules are radio access network (RAN) rules.

In example 14, the UE of examples 12-13 can be optionally configuredsuch that the 3GPP networks comprise global system for mobilecommunications (GSM) network, general packet radio services (GPRS)network, enhanced data rates for GSM Evolution (EDGE) network, universalmobile telecommunications system (UMTS) network, long term evolution(LTE) network or LTE advanced network.

In example 15, the UE of examples 12-14 can be optionally configuredsuch that the non-3GPP networks further comprise Wi-Fi networks orWi-Max networks.

In example 16, the UE of examples 12-15 can be optionally configuredsuch that the ANDSF rules comprise inter-system mobility policy (ISMP)rules, inter-system routing policy (ISRP) rules or inter-APN routingpolicy (IARP) rules.

In example 17, the UE of examples 12-16 can be optionally configuredsuch that obtaining the ANDSF rules further comprises obtaining theANDSF rules from a 3GPP network provider.

In example 18, the UE of examples 12-17 can be optionally configuredsuch that obtaining the ANDSF rules further comprises obtaining theANDSF rules from static pre-provisioned UE storage.

In example 19, the UE of examples 12-18 can be optionally configuredsuch that obtaining the ANDSF rules further comprises pre-provisioningthe ANDSF rules in the UE.

In example 20, the UE of examples 12-19 can be optionally configuredsuch that connecting to the non-3GPP network further comprises usingWLAN link control protocol (WLCP) to establish WLAN connections andrelease connections from the 3GPP network for the PDN connections tooffload.

Example 21 is a method for offloading cellular traffic to wireless localarea network (WLAN) traffic. The method includes receiving WLAN offloadconfiguration data. The method further includes receiving WLANidentifiers describing available wireless local area network accesspoints (WLAN APs) for offload of data connections. The method alsoincludes determining WLAN parameters for received WLAN identifiers. Themethod further includes receiving network provider rules that referencecellular parameters and the WLAN parameters. The method also includesevaluating the network provider rules based on the cellular parametersand WLAN parameters. The method further includes determining a set ofaccess networks available for use. The method also includes determiningwhether to connect to a WLAN AP in the set of access networks availablefor use. When connecting to a WLAN AP, the method includes determiningwhich data connections to offload to the WLAN AP.

In example 22, the method of example 21 can be optionally configuredsuch that the network provider rules are access network discovery andselection function (ANDSF) rules that include the cellular parametersand the WLAN parameters.

In example 23, the method of examples 21-22 can be optionally configuredsuch that the data connections are packet data network (PDN)connections.

In example 24, the method of examples 21-23 can be optionally configuredsuch that the network provider rules further comprise validity criteriathat describe WLAN parameter thresholds to compare with the WLANparameters.

In example 25, the method of examples 21-24 can be optionally configuredsuch that determining WLAN parameters further comprises receiving WLANparameters thresholds from a second protocol layer of a user equipment(UE) that is lower than a first protocol layer that evaluates thenetwork provider rules.

In example 26, the method of example 25 can be optionally configuredsuch that determining WLAN parameters comprises a comparison with athreshold performed in the second protocol layer.

In example 27, the method of example 25 can be optionally configuredsuch that determining WLAN parameters comprises a value and a thresholddetermined by the second protocol layer, and a comparison between thevalue and a threshold is performed in the first protocol layer as partof the evaluating network provider rules.

In example 28, the method of example 25 can be optionally configuredsuch that the second protocol layer is a radio resource control (RRC)layer, packet data convergence protocol (PDCP) layer, radio link control(RLC) layer or medium access control (MAC) layer.

In example 29, the method of example 25 can be optionally configuredsuch that the second protocol layer is an access stratum layer.

In example 30 the method of example 25 can be optionally configured suchthat the first protocol layer is ANDSF.

Example 31 is a method for moving traffic between a cellular network andwireless local area network (WLAN) traffic. The method includesdetermining available cellular network radio access networks (RANs). Themethod further includes receiving cellular offload configuration data.The method also includes receiving WLAN identifiers describing availablewireless local area network access points (WLAN APs). The method furtherincludes determining WLAN parameters for received WLAN identifiers. Themethod also includes receiving network provider information thatincludes cellular parameters. The method further includes evaluatingnetwork provider rules based on the cellular parameters and WLANparameters. The method also includes determining a set of accessnetworks available for use, the set of access networks comprising WLANAPs and cellular network RANs. The method further includes determiningwhether to connect to a cellular network RAN in the set of accessnetworks available for use. When connecting to a cellular network RAN,the method includes determining which data connections to offload to thecellular network RAN.

In example 32, the UE of example 31 can be optionally configured suchthat determining WLAN parameters further comprises receiving WLANparameters thresholds from a second protocol layer of a user equipment(UE) that is lower than a first protocol layer that evaluates thenetwork provider rules.

In example 33, the method of examples 31-32 can be optionally configuredsuch that receiving network provider information that includes thecellular parameters further comprises a comparison with a thresholdperformed in the second protocol layer.

In example 34, the method of examples 31-33 can be optionally configuredsuch that receiving network provider information that includes thecellular parameters further comprises a value and a threshold determinedby the second protocol layer, and a comparison between the value and athreshold is performed in the first protocol layer as part of theevaluating network provider rules.

In example 35, the method of example 34 can be optionally configuredsuch that the first protocol layer is higher than the second protocollayer.

In example 36, the method of examples 21-34 can be optionally configuredsuch that receiving WLAN parameter thresholds from a second protocollayer of a user equipment (UE) that is lower than a first protocol layerthat evaluates the network provider rules. The method can also beoptionally configured such that receiving cellular parameter thresholdsfrom a second protocol layer of a user equipment (UE) that is lower thana first protocol layer that evaluates the network provider rules. Themethod can be optionally configured such that performing a comparisonbetween a value and a threshold in the first protocol layer as part ofevaluating network provider rules. The method can also be optionallyconfigured such that determining a value and a threshold by a secondprotocol layer and performing a comparison between the value and athreshold in the first protocol layer as part of the evaluating networkprovider rules.

In example 37, the method of examples 21-34 can be optionally configuredsuch that the network provider rules further comprise one or more ofaccess network discovery and selection function (ANDSF) rules and radioresource control (RRC) rules.

Example 38 is an apparatus comprising means to perform a method asdescribed in any of examples 21-37.

Example 39 is machine readable storage including machine readableinstructions, when executed, to implement a method or realize anapparatus as claimed in any of claims 21-37.

Various techniques, or certain aspects or portions thereof, may take theform of program code (i.e., instructions) embodied in tangible media,such as floppy diskettes, CD-ROMs, hard drives, a non-transitorycomputer readable storage medium, or any other machine-readable storagemedium wherein, when the program code is loaded into and executed by amachine, such as a computer, the machine becomes an apparatus forpracticing the various techniques. In the case of program code executionon programmable computers, the computing device may include a processor,a storage medium readable by the processor (including volatile andnon-volatile memory and/or storage elements), at least one input device,and at least one output device. The volatile and non-volatile memoryand/or storage elements may be a RAM, an EPROM, a flash drive, anoptical drive, a magnetic hard drive, or other medium for storingelectronic data. The eNB (or other base station) and UE (or other mobilestation) may also include a transceiver component, a counter component,a processing component, and/or a clock component or timer component. Oneor more programs that may implement or utilize the various techniquesdescribed herein may use an application programming interface (API),reusable controls, and the like. Such programs may be implemented in ahigh-level procedural or an object-oriented programming language tocommunicate with a computer system. However, the program(s) may beimplemented in assembly or machine language, if desired. In any case,the language may be a compiled or interpreted language, and combinedwith hardware implementations.

It should be understood that many of the functional units described inthis specification may be implemented as one or more components, whichis a term used to more particularly emphasize their implementationindependence. For example, a component may be implemented as a hardwarecircuit comprising custom very large scale integration (VLSI) circuitsor gate arrays, off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. A component may also beimplemented in programmable hardware devices such as field programmablegate arrays, programmable array logic, programmable logic devices, orthe like.

Components may also be implemented in software for execution by varioustypes of processors. An identified component of executable code may, forinstance, comprise one or more physical or logical blocks of computerinstructions, which may, for instance, be organized as an object, aprocedure, or a function. Nevertheless, the executables of an identifiedcomponent need not be physically located together, but may comprisedisparate instructions stored in different locations that, when joinedlogically together, comprise the component and achieve the statedpurpose for the component.

Indeed, a component of executable code may be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different programs, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within components, and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set, or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, merely as electronic signals on a system ornetwork. The components may be passive or active, including agentsoperable to perform desired functions.

Reference throughout this specification to “an example” means that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one embodiment of the presentinvention. Thus, appearances of the phrase “in an example” in variousplaces throughout this specification are not necessarily all referringto the same embodiment.

As used herein, a plurality of items, structural elements, compositionalelements, and/or materials may be presented in a common list forconvenience. However, these lists should be construed as though eachmember of the list is individually identified as a separate and uniquemember. Thus, no individual member of such list should be construed as ade facto equivalent of any other member of the same list solely based onits presentation in a common group without indications to the contrary.In addition, various embodiments and examples of the present inventionmay be referred to herein along with alternatives for the variouscomponents thereof. It is understood that such embodiments, examples,and alternatives are not to be construed as de facto equivalents of oneanother, but are to be considered as separate and autonomousrepresentations of the present invention.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of materials, frequencies, sizes, lengths, widths, shapes,etc., to provide a thorough understanding of embodiments of theinvention. One skilled in the relevant art will recognize, however, thatthe invention may be practiced without one or more of the specificdetails, or with other methods, components, materials, etc. In otherinstances, well-known structures, materials, or operations are not shownor described in detail to avoid obscuring aspects of the invention.

Although the foregoing has been described in some detail for purposes ofclarity, it will be apparent that certain changes and modifications maybe made without departing from the principles thereof. It should benoted that there are many alternative ways of implementing both theprocesses and apparatuses described herein. Accordingly, the presentembodiments are to be considered illustrative and not restrictive, andthe invention is not to be limited to the details given herein, but maybe modified within the scope and equivalents of the appended claims.Those having skill in the art will appreciate that many changes may bemade to the details of the above-described embodiments without departingfrom the underlying principles of the invention.

The scope of the present invention should, therefore, be determined onlyby the following claims.

The invention claimed is:
 1. At least one non-transitorycomputer-readable storage medium having stored thereon instructionsthat, when executed by one or more processors, cause the one or moreprocessors to perform operations comprising: process radio accessnetwork (RAN) assistance parameters to identify a wireless local areanetwork (WLAN) for traffic offload; receive a first radio resourcecontrol (RRC) signal indicating a first packet data network (PDN)connection that is restricted from offload from a wireless wide areanetwork (WWAN) to the WLAN; and select the first PDN connection forcommunication only through the WWAN.
 2. The at least one non-transitorycomputer-readable storage medium of claim 1, wherein the RAN assistanceparameters comprise at least one of a WWAN threshold and a WLANthreshold.
 3. The at least one non-transitory computer-readable storagemedium of claim 1, wherein the WWAN threshold is selected from a firstgroup comprising a reference signal received power (RSRP) threshold, acommon pilot channel (CPICH) per chip over total noise power density(Ec/No) threshold, and reference signal received quality (RSRQ)threshold, and wherein the WLAN threshold is selected from a secondgroup comprising a beacon received signal strength indicator (RSSI)threshold, a backhaul data rate threshold, and a basic service set (BSS)load threshold.
 4. The at least one non-transitory computer-readablestorage medium of claim 1, wherein the WWAN comprises a third generationpartnership project (3GPP) network.
 5. The at least one non-transitorycomputer-readable storage medium of claim 4, wherein the WLAN comprisesa non-3GPP network.
 6. The at least one non-transitory computer-readablestorage medium of claim 1, further comprising to receive, from anevolved packet core (EPC) of the WWAN, access network discovery andselection function (ANDSF) rules including at least one of aninter-system routing policy (ISRP) rule or an inter-access point name(APN) routing policy (TARP) rule.
 7. The at least one non-transitorycomputer-readable storage medium of claim 6, wherein the ANDSF rulescomprise one or more threshold conditions or an offload preferenceindicator (OPI) condition.
 8. A apparatus of a user equipment (UE)configured for access network selection and traffic steering comprising:memory configured to store radio access network (RAN) assistanceparameters; a processor configured to: process the RAN assistanceparameters to identify a wireless local area network (WLAN) for trafficoffload; receive a first radio resource control (RRC) signal indicatinga first packet data network (PDN) connection that is restricted fromoffload from a wireless wide area network (WWAN) to the WLAN; and selectthe first PDN connection for communication only through the WWAN.
 9. Theapparatus of claim 8, wherein the processor is further configured to:receive a second RRC signal indicating a second PDN connection that isallowed to be offloaded from the WWAN to the WLAN; and select the secondPDN connection for communication through the WLAN based at least in parton the RAN assistance parameters.
 10. The apparatus of claim 8, furthercomprising: a first wireless interface to communicate through the WWAN;and a second wireless interface to communicate through WLAN.
 11. Theapparatus of claim 8, wherein the RAN assistance parameters comprise atleast one of a WWAN threshold or a WLAN threshold.
 12. The apparatus ofclaim 11, wherein the WWAN threshold is selected from a group comprisinga reference signal received power (RSRP) threshold, a common pilotchannel (CPICH) per chip over total noise power density (Ec/No)threshold, or a reference signal received quality (RSRQ) threshold. 13.The apparatus of claim 11, wherein the WLAN threshold is selected from agroup comprising a beacon received signal strength indicator (RSSI)threshold, a backhaul data rate threshold, or a basic service set (BSS)load threshold.
 14. An evolved packet core (EPC) of a wireless wide areanetwork (WWAN), comprising: memory configured to store offloadinformation; a processor configured to: generate the offload informationindicating one or more first packet data network (PDN) connectionsrestricted from offload from the WWAN to a wireless local area network(WLAN); communicate the offload information to a user equipment (UE);and communicate radio access network (RAN) assistance informationthrough radio resource control (RRC) to the UE, the RAN assistanceinformation including rules to determine whether to perform trafficoffloading to the one or more first PDN connections authorized foroffload from the WWAN to the WLAN.
 15. The EPC of claim 14, wherein theRAN assistance information comprises a WWAN threshold.
 16. The apparatusof claim 15, wherein the WWAN threshold is selected from a groupcomprising a reference signal received power (RSRP) threshold, a commonpilot channel (CPICH) per chip over total noise power density (Ec/No)threshold, or a reference signal received quality (RSRQ) threshold. 17.The EPC of claim 14, wherein the RAN assistance information comprises aWLAN threshold.
 18. The apparatus of claim 17, wherein the WLANthreshold is selected from a group comprising a beacon received signalstrength indicator (RSSI) threshold, a backhaul data rate threshold, ora basic service set (BSS) load threshold.